home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group01a.txt
/
000093_icon-group-sender _Fri Jul 7 07:44:18 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2002-01-03
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id HAA11378
for icon-group-addresses; Fri, 7 Jul 2000 07:42:22 -0700 (MST)
Message-Id: <200007071442.HAA11378@baskerville.CS.Arizona.EDU>
Date: Fri, 7 Jul 2000 14:43:26 +1200 (NZST)
From: "Richard A. O'Keefe" <ok@atlas.otago.ac.nz>
To: gep2@terabites.com, icon-group@optima.CS.Arizona.EDU, trollet@skynet.be
Subject: Re: Error messages
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
Content-Length: 762
Gordon Peterson <gep2@terabites.com> wrote (in extremely long lines):
> Although you COULD probably write [an assembler] in Prolog,
> I have to wonder if the benefits of making that choice are
> enough to justify the hassle.
I just _have_ to ask: WHICH hassle?
Let's face it, analysing the input hasn't been the hard part of assembler
writing for decades. Writing the output is the tricky part. The real
hassle is finding out what the wretched output is supposed to look like.
For UNIX (maybe Windows too; I've never used Cygwin) anyone wanting to write
a new kind of assembler would be mad not to re-use as much of the GNU binutils
as practical. By all means put a smart new front end on an assembler, but
let someone else deal with the *real* hassle.